Skip to content

fix: TypeScript's option checking return value should be noImplicitReturns#700

Closed
stefafafan wants to merge 1 commit intobasarat:masterfrom
stefafafan:noimplicitreturns
Closed

fix: TypeScript's option checking return value should be noImplicitReturns#700
stefafafan wants to merge 1 commit intobasarat:masterfrom
stefafafan:noimplicitreturns

Conversation

@stefafafan
Copy link
Copy Markdown

This following portion of the documentation is incorrect, strictNullChecks does not have to do with the "not all code paths return a value" check, it is noImplicitReturns that checks this.

If using strictNullChecks and doing exhaustive checks, TypeScript might complain "not all code paths return a value". You can silence that by simply returning the _exhaustiveCheck variable (of type never).
https://basarat.gitbook.io/typescript/type-system/discriminated-unions#strictnullchecks

Playground example:

@stefafafan stefafafan closed this by deleting the head repository Apr 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants